Field device commissioning system and field device commissioning method

ABSTRACT

A field device commissioning system, may include, but is not limited to, a commissioning tool. The commissioning tool is configured to communicate with a plurality of field devices and a repository. The commissioning tool is configured to: provide a user interface with at least one template of a plurality of templates in the repository for selection; determine, using at least one parameter in at least one of a control system loop information file and a field device information file in the repository, check functions for at least one of the plurality of field devices; provide the user interface with information which identifies at least one of the plurality of field devices for selection; and generate, using a selected template, tasks associated with the determined check functions for the selected at least one field device.

BACKGROUND

1. Fields of Invention

The disclosure of the invention relates to a field device commissioningsystem and a method of commissioning a field device in an industrialplant.

2. Backgrounds

Field Device

Typical examples of field devices are instruments or transmitters whichare used to obtain process variables in an equipment or part of anindustrial process in an industrial facility or plant. Some devices areused for specific process variables. For example, the field device canbe used as a temperature transmitter for temperature process variable, aflowmeter for flowrate process variable, and a pressure transmitter forpressure process variable.

Some field devices are configurable to be used for different types ofprocess variables. In some cases, pressure transmitters are configurablefor temperature process variable, flowrate process variable or pressureprocess variable. However, such devices can be configured to measureonly one designated process variable when in use.

There are many vendors manufacturing different types of field devices.To ensure compatibility, the field devices are configured to functionaccording to one of the standard communication protocols, such as HART,or Foundation Fieldbus. A field device which uses the HART communicationprotocol will be hereinafter be referred to as a HART field device, oneusing Foundation Fieldbus is FF-H1 field device.

Plant Management and Control System

A plant management and control system may typically include a devicemanagement system and a control system as shown in FIG. 1. Other systemsmay optionally be included in that system to perform otherfunctionalities.

A device management system acts as the central database for field devicemaintenance information. This information can include details aboutdevice parts, links to device documents, device description files,details about device inspection activities, device parameter history,and device messages. The device management system can also manage theinformation acquired from device calibration tools and applications bydownloading or synchronization. The device management system can managedevices connected to control systems for example:

-   -   (a) control system (such as CENTUM™); and    -   (b) safety-instrumented system (ProSafe-RS™)

Commissioning

In an industrial plant, a typical installation includes connecting fielddevices and equipment to a control system and/or a device managementsystem in a control room and performing configuration. After completionof the installation, the next step is a process for commissioning.Commissioning is a process for testing if the field devices, equipment,facility or industrial plant will perform one or more specifiedfunctions according to design objectives or specifications. Thecommissioning is done by performing a manual work check function. Thereare different manual work check functions. Different check functions aredone differently on different field devices. Examples of check functionsare as follows.

-   -   (a) Connection check is a check function that evaluates a        connection and a physical location of a field device in the        plant.    -   (b) Range comparison check is a check function that evaluates if        a range information setting on function blocks in a control        system for the plant matches a range information setting on a        field device.    -   (c) Linearization check is a check function that compares the        linearization type from the physical field device with an input        signal conversion for the field device in the control system.    -   (d) Input loop check is a check function that evaluates if a        field device which is configured to measure an input process        variable in an input loop is communicating with a control system        by reflecting in the control system, a test data written to the        field device.    -   (e) Output loop check is a check function that evaluates if a        control system is communicating with a field device configured        to measure an output process variable in an output loop, where        the evaluation is done by determining if the field device        reflects a test data written to a manipulative value of the        control system.

In the system of FIG. 1, commissioning of field devices is donemanually. A user who is doing commissioning work, has to decide manuallywhich check functions are done for each field device. Further, the userhas to decide manually how to perform each check function, such asdeciding which parameter to use, which results to read and how todetermine analyses of the results.

For testing of each field device for each commissioning task, at leasttwo persons, a field operator and a control room operator, have to be inclose communication with each other during throughout the testprocedure.

In an example of a linearization check shown in FIG. 2A, an engineerreads a linearization type of a field device manually from the physicalfield device using a device parameter reading tool. Then he reads aninput signal conversion parameter in a control system, which is usuallyin a function block of the control system. Finally he analyses thereadings and performs a comparison between the linearization type of thefield device and the input signal conversion parameter to determine ifthe linearization configuration is correct.

In another example of a manual connection check shown in FIG. 2B, acontrol room operator views a graphical user interface (“GUI”) while afield operator checks a physical field device. The control room operatorrequests the field operator to manually disconnect the field device froma network in the plant. After the field operator has disconnected thefield device, he informs the control room operator of the disconnection.Upon receipt of the information of the disconnection, the control roomoperator then verifies from the GUI that the field device has beendisconnected. When the disconnection is confirmed on the GUI, thecontrol room operator requests the field operator to connect the fielddevice from the network in the plant. Upon receipt of the request, thefield operator manually connects the field device to the network in theplant. After the field operator has connected the field device, heinforms the control room operator of the connection. Upon receipt of theinformation of the connection, the control room operator then verifiesfrom the GUI that the field device has been connected. Both the fieldoperator and the control room operator have to update each other as donefor the disconnection and connection processes. Both the control roomoperator and the field operator communicate with each other using aremote communication device such as a walkie-talkie. It is tedious forboth the control room operator and the field operator to be in constantcommunication for every step.

In a typical plant, there are hundreds of field devices, commissioningrequires a lot of manpower and time. When new equipment is added to thata plant, if the area is hazardous, extra coordination efforts will berequired during the commissioning process.

For each check function, a user needs to determine values to be setand/or configured on a field device. When there are multiple checkfunctions to be performed on the field device, the user has to decidethe sequence of settings and/or configurations of the test valuesmanually. A different sequence from a proper sequence may result inerrors or inaccurate test results. Manual actions, such as setting andconfiguration of test values, are prone to introducing human error andtime consuming. Documentation of check functions which have beencompleted and test results are done manually.

There is a need for an improved method and system for performingcommissioning of field device.

SUMMARY

A field device commissioning system, may include, a commissioning toolconfigured to communicate with a plurality of field devices and arepository. The commissioning tool is configured to: provide a userinterface with at least one template of a plurality of templates in therepository for selection; determine, using at least one parameter in atleast one of a control system loop information file and a field deviceinformation file in the repository, check functions for at least one ofthe plurality of field devices; provide the user interface withinformation which identifies at least one of the plurality of fielddevices for selection; and generate, using a selected template, tasksassociated with the determined check functions for the selected at leastone field device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a plant management and control system inthe related art.

FIGS. 2A and 2B are process workflows in the related art.

FIG. 3 is a block diagram of configurations of a field device managementsystem including a field device commissioning system according to someembodiments of the present invention.

FIG. 4 is a connection check workflow according to some embodiments ofthe present invention.

FIG. 5 is a table showing an example of a judgment table to be used fordetermining a linearization check result in commissioning according tosome embodiments of the present invention.

FIG. 6 is a linearization check workflow according to some embodimentsof the present invention.

FIGS. 7A and 7B are views which each illustrate an automatic generationof tasks workflow according to some embodiments of the presentinvention.

DETAILED DESCRIPTIONS

Reference will now be made in detail to the preferred embodiments of theinvention, examples of which are illustrated in the accompanyingdrawings. While some aspects of the invention will be described inconjunction with the preferred embodiments, it will be understood thatthey are not intended to limit the invention to these embodiments. Onthe contrary, the invention is intended to cover alternatives,modifications and equivalents, which may be included within the spiritand scope of the invention as defined by the appended claims.Furthermore, in the following detailed descriptions of the presentinvention, numerous specific details are set forth in order to provide athorough understanding of the present invention. However, it will beobvious to one of ordinary skill of the art that the present inventionmay be practiced without these specific details. In other instances,well known methods, procedures, components, and features have not beendescribed in detail as not to unnecessarily obscure aspects of thepresent invention.

In some embodiments of the present invention, a field devicecommissioning system is described using the most commonly used checkfunctions, such as connection check, range comparison check,linearization check, input loop check and output loop check. In general,these check functions can be automated by any available tools. A manualcheck, which is another type check function that allows a user to createinstructions for tasks which cannot be automated by any tool, is alsoincluded in the descriptions.

Firstly, tasks are used to define a unit of work or procedure. One checkfunction is defined by one task. When a check function is defined by onetask, the defined task is associated with that check function.

FIG. 3 is a block diagram of a field device management system 1000 insome embodiments of the present invention. The field device managementsystem 1000 includes field devices 120 and 125, a control system 140, afield device commissioning system 100, and a repository 130. The controlsystem 140 is configured to communicate with the field devices 120 and125 in the field and to control the field devices 120 and 125. The fielddevice commissioning system 100 is configured to communicate with thecontrol system 140, the repository 130 and the field devices 120 and125. The field device commissioning system 100 is configured to referfiles stored in the repository 130 and to perform automaticcommissioning processes for the field device 120 or 125. The fielddevice commissioning system 100 includes at least a commissioning tool110 which is configured to communicate with the field device 120 or 125and with the repository 130 as well as with the control system 140. Thecommissioning tool 110 is configured to refer files stored in therepository 130 and to perform automatic commissioning processes for thefield device 120 or 125. The commissioning tool 110 can be implementedby software in combination with hardware. In general, the control system140 and the field device commissioning system 100 may be placed in acontrol room 150. In some cases, the field device commissioning system100 may include the repository 130 in addition to the commissioning tool110. In other cases, the field device commissioning system 100 may notinclude the repository 130, where the repository 130 may be in aseparate system or a server of a remote location.

In general, the repository 130 may be configured to have a field deviceinformation file 132, a registration file 134, a protocol deviceregistration file 136, a control system loop information file 138 andany other temporary or permanent files, if any.

The field device information file 132 has a list of field devices whichare configured to be in communication with the field devicecommissioning system 100, and describes multiple properties for eachfield device. Examples of the multiple properties are “device tag”,“device model”, “device ID”, “manufacturer/vendor ID” and “revision No”.

The registration file 134 lists, for each field device, devicecommunication commands which are to be executed to the respective fielddevice 120, 125 for a desired task or check function. The field deviceinformation file 132 can be referred by the commissioning tool 110 toallow the commissioning tool 110 to perform a task to identify a type ofthe field device, for example, whether the field device is a pressuretransmitter, a temperature transmitter or a flowmeter. The registrationfile 134 can be referred by the commissioning tool 110 to allow thecommissioning tool 110 to identify a device communication command “HARTCommand 54”, and then to execute it to the HART field device.

The protocol device registration file 136 lists field devices which areregistered in a respective protocol database. In some cases, theprotocol device registration file 136 may include only field deviceswhich are pressure transmitters. For example, HART field devices may beregistered with HART communication foundation. A HART field deviceregistration file is created from HART field devices which areregistered with the HART communication foundation. For FoundationFieldbus H1 (“FF-H1”) field devices which are registered in the Fieldbusfoundation, a corresponding FF-H1 registration file is created. Theprotocol device registration file 136 can be implemented as separatefiles, one for each protocol. Alternatively, the protocol deviceregistration file 136 can be implemented as one file including fielddevices registered in all protocols with a suitable identifier todistinguish the respective protocols for the respective field devices.

The control system loop information file 138 lists, for each fielddevice, the respective configuration parameters in the control system140. In the control system 140 which has function blocks, the functionblocks information and association of function with the field devicesare included in the control system loop information file 138. Theassociation of the function blocks with the field devices is included asa mapping table. The control system loop information file 138 is updatedto the repository 130 when required, such as for each change in anyfield device or configuration parameters in the control system 140. Theupdate is done by importing the control system loop information file 138as the need arises.

Connection Check

In one embodiment of the invention to perform a connection check, thecommissioning tool 110 is configured to retrieve at least one propertyfrom the field device 120 or 125. The retrieved property of the fielddevice 120 or 125 can be any one of “device tag”, “device model, “deviceID”, “manufacturer/vendor ID” and “revision No”. Preferably, theretrieved properties are “device model”, “manufacturer/vendor ID” and“revision No”. If the at least one property is retrieved successfully,this confirms that the commissioning tool 110 is connected to either oneof the field devices 120 and 125. However, there is a need to confirm ifthe correct connection is established between the commissioning tool 110and the correct one of the field devices 120 and 125.

The commissioning tool 110 is configured to compare the retrievedproperty and those properties in the field device information file 132to determine if there is any match between the retrieved property andthe properties in the field device information file 132. If more thanone property is retrieved, all the retrieved properties are compared tothe properties in the field device information file 132. Thecommissioning tool 110 is determined to be correctly configured tocommunicate with an expected one of the field devices 120 and 125, ifthe commissioning tool 110 determines that there is a match.

The commissioning tool 110 is also configured to compare the retrievedproperty with those in the registration file 134 to determine if thereis any match between the retrieved property and the properties in theregistration file 134. The commissioning tool 110 is configured toperform a first test which is a display test when the commissioning tool110 determines that there is a match between the retrieved property withthose in the registration file 134. The display test is consideredsuccessful when a desired output is shown on the display of the fielddevice. Since the display unit is usually a liquid-crystal display, thistest is also referred to as the LCD test.

LCD Test for HART Field Device

To perform the LCD test for a HART field device, the commissioning tool110 is configured to identify a device communication command, from theregistration file 134, which is suitable for performing the LCD test.The commissioning tool 110 is further configured to execute theidentified device communication command to the field device, andretrieve a response from the field device. This response is the same asan output which the field device generates on the LCD display. Thecommissioning tool 110 is configured to generate an output of theretrieved response to be supplied to a user interface in the controlroom 150 to a control room operator to see the results of the LCD teston the user interface without communicating with a field operator. Thiswill improve the efficiency of the connection test in terms of time andmanpower. The field operator can view the output of the retrievedresponse on the LCD display of the field device too.

LCD Test for FF-H1 Field Device

To perform the LCD test for a FF-H1 field device, the commissioning tool110 is configured to identify a parameter index and a parameter indexvalue from the registration file 134 using the retrieved at least oneproperty of the field device, thereby retrieving the identifiedparameter index and the parameter index value. The commissioning tool110 is further configured to execute a write command to the fielddevice. The write command is to write the retrieved parameter indexvalue to the retrieved parameter index of the field device. If the writecommand fails to write to the parameter index, an error message is sentto the commissioning tool 110. The commissioning tool 110 is configuredto detect an error message. When the error message is detected by thecommissioning tool 110, a predefined error message is supplied from thecommissioning tool 110 to the user interface in the control room 150. Ifthe write command writes successfully, the field device generates adesired output on the LCD display. An example of the desired output is apreset pattern. When no error message is detected by the commissioningtool 110, the commissioning tool 110 is configured to generate thepreset pattern to be supplied to the user interface in the control room150.

Thus, the commissioning tool 110 in cooperation with the user interfacewill allow a control room operator to see the results of the LCD test onthe user interface without communicating with a field operator. Thiswill improve the efficiency of the connection test in terms of time andmanpower. The field operator can view the output of the retrievedresponse on the LCD display of the field device too.

The commissioning tool 110 is configured to perform the followingreferring and determining processes, if the commissioning tool 110determines that there is no match between the retrieved property withthose in the registration file 134. The commissioning tool 110 isconfigured to refer a communication protocol of the field device from acontrol system loop information file 138 in the repository 130, and todetermine if the retrieved property is for a predetermined field device,such as a HART field device. A HART field device uses HART communicationprotocol. The commissioning tool 110 is configured to perform a secondtest which is different from the first test, when the commissioning tool110 determines that the retrieved property is for a predetermined fielddevice. The commissioning tool 110 is then configured to execute apredetermined device communication command, such as “HART command 72”,to the field device. This command is for performing a SQUAWK test on aHART field device. A HART field device usually generates a visual,audible, or mechanical response to a successful SQUAWK test. Thecommissioning tool 110 is configured to receive a response from thefield device and supply the response to a user interface in the controlroom 150. Similar to the LCD test, the commissioning tool 110 incooperation with the user interface will allow a control room operatorto see the results of the LCD test on the user interface withoutcommunicating with the field operator. This will improve the efficiencyof the connection test in terms of time and manpower. The field operatorcan be notified by the output of the field device, such as from “SQUAWK”being displayed on the LCD display, too.

The commissioning tool 110 is configured to perform a third test whichis different from the first and second tests if the commissioning tool110 determines that the retrieved property is not for a predetermineddevice. In the third test, the commissioning tool 110 is configured togenerate a first instruction on a user interface to disconnect the fielddevice from the field device commissioning system 100. The commissioningtool 110 is configured to receive a first response from the fielddevice, when the field operator has completed the first instruction. Anexample of the first response is a message that the field device hasbeen disconnected from the field device commissioning system 100.

The commissioning tool 110 is further configured to generate a secondinstruction on the user interface to connect the field device to thefield device commissioning system 100. The commissioning tool 110 isconfigured to receive a second response from the field device when thefield operator has completed the second instruction. An example of thesecond response is a message that the field device has been disconnectedfrom the field device commissioning system 100. The commissioning tool110 is further configured to determine a status of the field devicebased on the first or second response and generate an output of thedetermined status to be supplied to the user interface. Optionally, thethird test can be repeated multiple times.

For each of the first, second and third tests, the commissioning tool110 is configured to provide an option to the user interface toacknowledge a test result. If there is an error on performing the test,the test result is “Failed” and no acknowledgement option is provided bythe commissioning tool 110. The commissioning tool 110 may be configuredto make the user interface request the user to acknowledge the testresult when the test is completed without an error. This is to ensurethat the test has been completed successfully.

The commissioning tool 110 is configured to identify a test result as“Failed”. Examples of such cases are: (1) when there is no propertyretrieved from the field device, (2) there is no match for the retrievedproperty with those in the field device information file 132. When thecommissioning tool 110 identifies a test result as failed, thecommissioning tool 110 provides a test result “Failed” to the userinterface and the test result is updated in a temporary or permanentfile in the repository 130.

FIG. 4 is a connection check workflow 200 which is a method of operationfor a connection check function according to one embodiment of theinvention, performed in the field device commissioning system 100. InStep 210, the commissioning tool 110 retrieves at least one propertyfrom the field device 120 or 125 to check if the commissioning tool 110can communicate with the field device 120, 125. This is to determine ifthe Commissioning Tool 110 is connected to the field device 120, 125.When the property is retrieved successfully, the commissioning tool 110is determined to be connected to the field device 120, 125.

In Step 220, by the commissioning tool 110, the at least one retrievedproperty from the field device is compared with properties in a fielddevice information file 132 to determine if there is any match. Whenthere is a match, the operation will go on to Step 230. In Step 230, bythe commissioning tool 110, at least one of the retrieved property iscompared with properties in the field device information file 132 todetermine if there is a match.

When the commissioning tool 110 determines that there is a match in Step230, then proceed to Step 232 to perform the first test by thecommissioning tool 110. In the first test, the steps by thecommissioning tool 110 are to identify, from the registration file 134,a device communication command for the field device which is associatedwith the retrieved property. Then the commissioning tool 110 executesthe identified device communication command to the field device. Afterexecuting the device communication command, the commissioning tool 110receives a response from the field device and generates an output of thereceived response to be supplied to the user interface.

When there is no match in Step 230, the commissioning tool 110 comparesa communication protocol of the field device with that in the controlsystem loop information file 138 to determine if the communicationprotocol is for a predetermined field device, such as a HART fielddevice. When the communication protocol is determined to be for thepredetermined field device, then proceed to Step 234 to perform a secondtest which is different from the first test.

In the second test, the commissioning tool 110 executes a predetermineddevice communication command to the field device. When the field deviceis a HART field device, the commissioning tool 110 executes a “HARTCommand 72”. When the field device receives the predetermined devicecommunication command, the field device generates one of a visual,audible or mechanical response, such as display of “SQUAWK” on fielddevice LCD display, which can be received by a field operator. Inaddition, the operation further includes receiving from the field devicea response to the executed device communication command and generatingan output of the received response to be supplied to the user interface.

When by the commissioning tool 110 the communication protocol isdetermined to be not for the predetermined field device, then proceed toStep 236 to perform, by the commissioning tool 110, a third test whichis different from the first and second tests. In the third test, themethod by the commissioning tool 110 is to generate a first instructionon a user interface to disconnect the field device from the field devicecommissioning system 100. The control room operator communicates this tothe field operator. After the field operator has completed thedisconnection, the next step by the commissioning tool 110 is to receivea first response from the field device and generate a second instructionon the user interface to connect the field device 120, 125 to the fielddevice commissioning system 100. Similarly, the control room operatorcommunicates this to the field operator. After the field operator hascompleted the connection, the operation by the commissioning tool 110continues to determine a status of the field device 120, 125 based onthe second response and generates an output of the determined status tobe supplied to the user interface.

For each of the first, second and third tests, if the tests arecompleted without errors by the commissioning tool 110 and the user hasacknowledged the test result as being “Passed”, Step 240 updates thecommissioning tool 110 determines if an update on device properties tothe field device information file 132 in the repository 130 isnecessary. When an update is necessary, the device information isretrieved by the commissioning tool 110 from the field device for theupdate of the field device information file 132 in the repository 130.This is useful to have updated device properties in the field deviceinformation file 132 for other check functions, such as linearizationcheck. It would be also useful for other applications in the devicemonitoring system, control system or any other systems.

The above embodiments of the invention support automation of fielddevice communication check, field device information check and update.By automation, human errors are reduced. Further, an embodiment of theinvention may automatically select one of at least three predeterminedtests based on field device information, which also improves theaccuracy of the test results. Since prior configuration is done, thechecks are done and results are recorded automatically. Advantageously,the manpower is reduced and accordingly there is time and cost savings.With the reduction of the need for manual field operations, there isreduced risk for field operators.

Linearization Check

Another embodiment of the invention is to perform a linearization checkon a field device 120, 125. The commissioning tool 110 is configured todetermine, from the control system loop information file 138, if thefield device 120, 125 is configured as an input device. This is based onreading a configuration parameter in the control system loop informationfile 138. Preferably, the configuration parameter describes a connectiontype of the field device. For example, if the connection type is “IN”,then it is determined to be configured as an input device, if theconnection type is “OUT”, then it is configured as an output device.

In an alternative, the connection type of the field device can bedetermined by retrieving a configuration parameter value from thecontrol system 140. The configuration parameter is “Connection Type”.For example, if the connection parameter value is “IN”, then it isdetermined to be configured as an input device. If the connectionparameter value is “OUT”, then it is configured as an output device.

When the field device is determined to be configured as the inputdevice, the commissioning tool 110 determines from the protocol deviceregistration file 136, if the field device is a pressure transmitter.Based on the communication protocol of the field device in the controlsystem loop information file 138, the commissioning tool 110 identifiesthe communication protocol of the field device.

When the identifier of the field device is not in the protocol deviceregistration file 136, the determination cannot be done. Examples of anidentifier are “Device Model” and “Manufacturer/Vendor ID”. Thecommissioning tool 110 is configured to retrieve information from othersources which are suitable to determine if the field device 120, 125 isa pressure transmitter.

For a HART Field Device

For a HART field device, the commissioning tool 110 is furtherconfigured to identify, from the registration file 134, a predetermineddevice command for retrieving the information. The commissioning tool110 is configured to execute the identified predetermined device commandto the field device, receive a response from the field device anddetermine if the field device is a pressure transmitter from thereceived response.

In a first example, the predetermined command is “HART Command 54”. Theresponse is a package which includes many bytes. The response byte 21represents “Device Variable Family”. When the response byte 21 has avalue “5”, then the field device is determined to be a pressuretransmitter device. Alternatively, the determination can be done from aresponse byte 22 which represents “Device Variable Classification”. Whenthe response byte 22 has a value “65”, the field device is determined tobe a pressure transmitter.

In a second example, the predetermined command is “HART Command 1”. Ifthe HART field device is revision 7 or any earlier revision, and theresponse value is within ranges of “1-14”, “145”, “237-239”, the fielddevice is determined to be a pressure transmitter. If the HART fielddevice is revision 6 and 7, and the response value is also within arange “170-179”, the field device is determined to be a pressuretransmitter.

Yet another alternative is to configure the commissioning tool 110 toread a predetermined variable in a database 160 (not shown) in thecommissioning tool. An example of the database 160 is an object linkingand embedding (OLE) for process control (“OPC”) database which readsfield device parameters periodically and updates in the database 160. Inthis example, the commissioning tool 110 is configured to read thepredetermined variable which represents an engineering unit, “_PV_Unit”.If the value is within ranges of 1-14, 145, 237-239, the field device isdetermined to be a pressure transmitter. If the HART field device is ofrevision 6 and 7, and the response value is also within a range“170-179”, the field device is determined to be a pressure transmitter.

In a preferred embodiment, if the response is not sufficient todetermine if the field device is a pressure transmitter device, thecommissioning tool 110 is configured to determine using anypredetermined methods. In a third example, the first and second examplesare implemented together sequentially.

For FF-H1 Field Device

For a FF-H1 field device, the commissioning tool 110 is furtherconfigured to read a predetermined variable in the database 160. Anexample of the database 160 is an object linking and embedding (OLE) forprocess control (“OPC”) database which reads field device parametersperiodically and updates in the database 160. In this example, thecommissioning tool 110 is configured to read the predetermined variablewhich represents a standard parameter, “_TB01.TRANSDUCER_TYPE”. Whenvalue of the standard is “100”, the field device is determined to be apressure transmitter.

Alternatively, the commissioning tool 110 is further configured toretrieve a predefined parameter from the field device. The commissioningtool 110 is configured to identify from the registration file 134 apredetermined device command for retrieving the information. Thecommissioning tool 110 is configured to execute the identifiedpredetermined device command to the field device, receive a responsefrom the field device and determine if the field device is a pressuretransmitter from the received response. For example, the commissioningtool 110 is configured to execute “parameter index” which indexes to astandard parameter, “_TB01.TRANSDUCER_TYPE”. When response is “100”, thefield device is determined to be a pressure transmitter.

Identify Exceptional Pressure Transmitter

Some field device manufacturer/vendor of pressure transmitters haveincluded additional functionalities such as mass-flow conversion, oradditional parameter to configure the usage of the field device. Suchfield devices are considered exceptional pressure transmitters.Therefore, it is preferable to identify the manufacturer/vendor anddevice model of such exceptional pressure transmitters to improveaccuracy of performing linearization check automatically. Themanufacturer/vendor and device model are identified from field deviceparameters such as “Manufacturer/Vendor ID” and “Device Type”.

-   -   (a) Preferably, the commissioning tool 110 is further configured        to determine if the field is an exceptional pressure        transmitter, by identifying if the field device has any one of        following parameters or combination of parameters:        -   (1) For a HART field device, a “Manufacturer/Vendor ID”            parameter is 0x000037 and “Device Type” parameter is 0x3754.        -   (2) For a FF-H1 field device, a “Manufacturer/Vendor ID”            parameter is 0x594543 and “Device Type” parameter is 0x000E.    -   (b) Still preferably, when the field device is identified to        have the parameters in above (3) and (4), the commissioning tool        110 is configured to determine, from the field device, if the        field device is configured to measure flow.

For a HART field device, the commissioning tool 110 is configured todetermine, from the registration file 134, the predetermined devicecommunication command. In this case, the predetermined devicecommunication command is “HART COMMAND 172”. When the commissioning tool110 receives a response “0x02”, the field device is configured tomeasure the flowrate.

For a FF-H1 field device, the commissioning tool 110 is configured toretrieve, from the field device, the value for parameter“_TB01.PRIMARY_VALUE_TYPE” or is “_TB01.LINEARIZATION”. When the valueis “0xfff2” for the former and “0x02” for the latter, the field deviceis configured to measure the flowrate.

To Check if Field Device is Configured to Measure Flow

When the field device is determined to be a pressure transmitter, thecommissioning tool 110 is further configured to determine, from thecontrol system loop information file 138, if the field device isconfigured in the control system 140 to measure flow.

An example of determination is by reading an engineering unit of aprocess variable which the field device is configured to measure. If theengineering unit is defined in terms of volume per time unit, such ascubic metre per second, minute, hour or day, the field device isconfigured in the control system 140 to measure flow.

Another example of determination is by reading parameter “Tag Name”.When the value of parameter “Tag Name” has any of the followingcharacters “FI”, “FFI”, “FQI”, “FZI”, “FC”, “FFC”, “FQC”, “FZIC”, “FIC”,“FFIC”, “FQIC”, “FZIC”, “FRC”, “FFRC”, “FQRC” and “FZRC” in combinationwith other characters or numbers, the field device is configured in thecontrol system 140 to measure flow.

Determine Linearization Type of Field Device Configured in ControlSystem

When the field device is determined to measure the predetermined processvariable, the commissioning tool 110 is further configured to determine,from the control system loop information file 138, a linearization type170 (not shown) in the control system 140 which is associated to thefield device.

In an example, a configuration parameter “Input Signal Conversion”, inthe control system loop information file 138, for the field device hasthe value “Linear”, and the linearization type is determined as“Linear”; for other values, the linearization type is “Other”. There maybe multiple values for the configuration parameter which represents thelinearization type, such as “Linear”, Square Root”, “Indirect SquareRoot”. Preferably, a mapping table is provided to enable thedetermination of the field device linearization type 170 in the controlsystem. The mapping table lists information for configuration parametersin the control system. For example, to determine a linearization type ofa field device in the control system, the linearization type is found inthe value of “Input Signal Conversion”. If the value is “Linear”, thenthe linearization type is determined as “Linear”. If the value is one of“Square Root”, “Indirect Square Root”, then the linearization type isdetermined as “Other”.

Alternatively, the commissioning tool 110 is configured to retrieveconfiguration parameter value from the control system 140 to determinethe linearization type 170.

For example, a configuration parameter “Input Signal Conversion”, in thecontrol system 140, for the field device has the value “No Conversion”,the linearization type is determined as “Linear”; for other values, thelinearization type is “Other”. There may be multiple values for theconfiguration parameter which represents the linearization type, such as“No Conversion”, “Square Root”, “Indirect Square Root”. Preferably, amapping table is provided to enable the determination of the fielddevice linearization type 170 in the control system. The mapping tablelists information for configuration parameters in the control system.For example, to determine a linearization type of a field device in thecontrol system, the linearization type is found in the value of “InputSignal Conversion”. If the value is “No Conversion”, then thelinearization type is determined as “Linear”. If the value is one of“Square Root”, “Indirect Square Root”, then the linearization type isdetermined as “Other”.

Determine Linearization Type of Field Device Configured in Field Device

The commissioning tool 110 is also configured to retrieve alinearization type 175 (not shown) of the field device from the fielddevice.

For a HART field device, the commissioning tool 110 is furtherconfigured to identify from the registration file 134, a predetermineddevice communication command. In this case is “HART COMMAND 15”, thecommissioning tool 110 executes it to the field device, and receives aresponse from the field device.

For example, if the retrieved response from the field device has value“0” for parameter “pressure_output_transfer_function”, the linearizationtype 175 of the field device is “Linear”. For all other values, thelinearization type 175 is “Other”.

For a FF-H1 input field device, the commissioning tool 110 is furtherconfigured to read from the field device of Input type, parameter“_AI01.L_TYPE”; for an FF-H1 output field device is“_TB01.POSITION_CHAR_TYPE”.

From the received response, the linearization type 175 of the fielddevice is identified from the registration file 134. For example, inputtype field device parameter of ““AI01.L_TYPE” with value “1” is a“Direct” field device, from the registration file 134, the linearizationtype 175 of the field device is identified as “Linear”. For all othervalues, the linearization type 175 is “Other”. Output field deviceparameter of “TB01.POSITION_CHAR_TYPE” with value “1” is a “Direct”field device, from the registration file 134, the linearization type 175of the field device is identified as “Linear”. For all other values, thelinearization type 175 is “Other”.

Preferably, a mapping table is provided in the repository 138 to enablethe determination of the field device linearization type 175 in thefield devices to be done conveniently.

Linearization Check Result

The commissioning tool 110 is further configured to determine, using thelinearization type 175 of the field device and the linearization type170 of the field device in the control system 140, a linearization checkresult.

The linearization check result is determined, for the field devicedetermined as described above, by applying predefined Logic in FIG. 5and using one of the following Scenarios:

-   -   Scenario 1: For a field device which is configured as:        -   1.1 Input device which is not pressure transmitter.        -   1.2 Input devices which are exceptional pressure            transmitters such as            -   a. a HART field device, which has a “Manufacturer/Vendor                ID” parameter is 0x000037 and “Device Type” parameter is                0x3754.            -   b. a FF-H1 field device, which has a                “Manufacturer/Vendor ID” parameter is 0x594543 and                “Device Type” parameter is 0x000E.    -   Scenario 2: For a field device which is a pressure transmitter,        the field device is configured to measure one of a process        variable, pressure and level.    -   Scenario 3: For a field device which is pressure transmitter and        configured to measure a flow process variable.    -   Scenario 4: For a field device which is a pressure transmitter        and cannot be determined to be configured to measure a flow        process variable.    -   Scenario 5: For a field device configured as output device which        processes output signals to actuators, such as valves.    -   For Scenario 1, applying Logic 1 in FIG. 5, when both        linearization types 170 and 175 are “Linear”, then the        linearization check result is good, represented by “OK” in FIG.        5. For other types of combination, the linearization check        result is not good, which can be represented by “NG” in FIG. 5.    -   For Scenario 2, applying Logic 2, when both linearization types        170 and 175 are “linear”, then a message is supplied on a user        interface for the Control Room Operator to determine the        linearization check, represented by “ACK” in FIG. 5. For other        types of combination, the linearization check result is not        good, represented by “NG” in FIG. 5.    -   For Scenario 3, applying Logic 3, when both linearization types        170 and 175 are the same, “Linear” or “Other”, then the        linearization check result is not good, represented by “NG” in        FIG. 5. For other types of combination, the linearization check        result is good, represented by “OK” in FIG. 5.    -   For Scenario 4, applying Logic 4, when both linearization types        170 and 175 are the same, “Linear” or “Other”, then the        linearization check result is not good, represented by “NG” in        FIG. 5. For other types of combination, a message is supplied on        a user interface for the control room operator to determine the        linearization check, represented by “ACK” in FIG. 5.    -   For Scenario 5, applying Logic 5, when both linearization types        170 and 175 are “Other”, then the linearization check result is        good, represented by “OK” in FIG. 5. For other types of        combination, the linearization check result is not good,        represented by “NG” in FIG. 5.

Preferably, the commissioning tool 110 is further configured todetermine the linearization check result using a judgment table 180 inthe repository 130 or in the commissioning tool 110. An example of thejudgment table 180 is illustrated in FIG. 5.

FIG. 6 is a linearization check workflow 300 which is a method ofperforming linearization check function according to one embodiment ofthe invention, in the field device commissioning system 100. In Step 310the commissioning tool 110 determines, from a control system loopinformation file 138, if the field device is configured to use as aninput device. The determination is done by verifying if the field deviceis using an input signal.

When the field device is determined to be the input device, in Step 320,the commissioning tool 110 determines, from a protocol deviceregistration file 136, if the field device is a pressure transmitter.

When the field device is determined to be the pressure transmitter, inStep 330, from the control system loop information file 138, thecommissioning tool 110 determines if the field device is configured inthe control system 140 to measure flow.

When the field device is determined to measure the predetermined processvariable, in Step 340, from the control system loop information file138, the commissioning tool 110 determines a linearization type 170 ofthe field device which is configured in the control system 140. In Step350, the commissioning tool 110 retrieves a linearization type 175 ofthe field device from the field device.

In Step 360, the commissioning tool 110 determines a linearization checkresult by using the linearization types 170, 175.

The above embodiments of the invention enable automatic retrieval,analysis and comparison of linearization types 170,175 of field devicesconfigured in the control system 140 and the field device 120, 125. Byautomation, human errors are reduced. Since prior configuration is done,the checks are done and results are recorded automatically.Advantageously, the manpower is reduced and accordingly there is timeand cost savings. With the reduction of the need for manual fieldoperations, there is reduced risk with less field operators required.

Automatic Generation of Tasks

Another embodiment of the invention is that the commissioning tool 110is configured to provide a user interface with at least one template ofmultiple templates in the repository 130. The multiple templates in therepository 130 are task templates and workflow templates. A tasktemplate is a task which is saved as a template. Accordingly, a workflowtemplate is a workflow which is saved as a template.

Further a task or workflow template includes a predefined value for thetask. For a task which has a configuration with multiple values, thereare predefined values for the configuration. Preferably, an option isprovided to change the predefined value.

A user, such as the control room operator, can select any of the task orworkflow templates provided on the user interface.

The commissioning tool 110 is configured to determine check functionsfor at least one of the plurality of field devices. To determine checkfunctions, the commissioning tool 110 is configured to readconfiguration parameters in the control system loop information file138, or parameters in the field device information file 132. Both filesare in the repository 130.

The commissioning tool 110 is configured to retrieve identifiers of thefield devices 120, 125 in the field device information file 132. Usingthe identifiers, from the control system loop information file 138, thecommissioning tool 110 determines if the field devices 120, 125 areassociated or connected to the control system 140.

In the control system 140 which has a function block 190 (not shown) forconnection to field devices. Preferably, it is further configured todetermine if the field devices 120, 125 are associated or connected to afunction block 190 in the control system 140.

The commissioning tool 110 is configured to determine check functions,associated with the selected task template or workflow template, for thefield devices 120, 125. In an example, the check functions aredetermined by using the following predetermined criteria in therespective sequence:

Sequence 1 is a “Connection Check Function” and the criteria are:

-   -   (a) Communication protocol of the field device is “HART” or        “FF-H1”, and    -   (b) Connection type of the field device is “Input” or “Output”.        Sequence 2 is a “Linearization Check Function” and the criteria        are:    -   (a) Field device is associated with the control system or        function block in the control system,    -   (b) Communication protocol of the field device is “HART” or        “FF-H1”, and    -   (c) Connection type of the field device is “Input” or “Output”.        Sequence 3 is a “Range Check Function” and the criteria are:    -   (a) For HART field device, it is associated with the control        system or function block in the control system,    -   (b) Communication protocol of the field device is “HART” or        “FF-H1”, and    -   (c) Connection type of the field device is “Input” or “Output”.        Sequence 4 is an “Input Loop Check Function” and the criteria        are:    -   (a) Field device is associated with the control system or        function block in the control system,    -   (b) Communication protocol of the field device is “HART” or        “FF-H1”, and    -   (c) Connection type of the field device is “Input”.        Sequence 5 is an “Output Loop Check Function” and the criteria        are:    -   (a) Field device is associated with the control system or        function block in the control system,    -   (b) Communication protocol of the field device is “HART” or        “FF-H1”, and    -   (c) Connection type of the field device is “Output”.        Sequence 6 is a “Manual Work Check Function” and the criteria        are:    -   (a) Communication protocol of the field device is “HART” or        “FF-H1”, and    -   (b) Connection type of the field device is “Input” or “Output”.

A summary of the criteria is provided in the Table 1 below.

TABLE 1 Criteria (AND) Is Field Device associated to Control SystemCommunication Connection Check Function Protocol of the Type of theSequence Functions Block? Field Device Field Device 1 Connection N/AHART, FF H1 Input, Check Output 2 Linearization YES HART, FF H1 Input,Check Output 3 Range Check YES for HART, FF H1 Input, HART Output N/Afor FF-H1 4 Input Loop YES HART, FF H1 Input Check 5 Output Loop YESHART, FFH1 Output Check 6 Manual Work N/A HART, FF H1 Input, CheckOutput

If the criteria are not satisfied, the corresponding check function isnot created. This prevents irrelevant check functions from beingexecuted, thus avoiding errors due to execution of irrelevant checkfunctions. Check functions may be omitted from a sequence for a fielddevice if the criteria are not satisfied. The sequence is the order forperforming the generated check functions. This creates a standardizedsequence to reduce error due to illogical sequence. The order of thesequence is such that Sequence 1 is done first and Sequence 6 last.

The commissioning tool 110 is configured to provide a user interfacewith information which identifies the field devices for selection. Theinformation is an identifier or a symbol which represents the fielddevice.

The commissioning tool 110 is configured to provide a user interfacewith group types for selection. The group types are stored in therepository 130. This is to generate the tasks in a group type accordingto preference of the user. An example of a group type is folder for anarea, a process, equipment or unit; another group type is checkfunction, user, team, and field devices.

Based on the selected template and group type, tasks associated with thedetermined check functions are generated automatically. The generatedtasks are provided on the user interface with information about thegenerated tasks. Preferably, the user interface is provided with thegenerated tasks and the user interlace is provided with an option tore-select the group type.

Preferably, the generated check functions are filtered using the earlierselected template. In this case, tasks are generated for a selectedsingle task template or workflow template.

FIG. 7A is a flow chart of a method 400 for automatically generatingtasks for a plurality of field devices according to an embodiment of theinvention. In Step 410, the commissioning tool 110 provides a userinterface with at least one template in the repository 130 forselection. Preferably, all the templates in the repository 130 areprovided.

In Step 420, at least one control system parameter is used to determinewhich check functions are associated with the field device. The controlsystem parameter is retrieved from either the control system loopinformation file 138 or the field device information file 132 in therepository 130. Not all check functions in the selected template can beapplied to all types of field devices. Based on the selected template inStep 410, predefined criteria such as those in above Table 1 are used todetermine the check functions. This prevents irrelevant check functionsfrom being executed, thus avoiding errors due to execution of irrelevantcheck functions.

In Step 430, the commissioning tool 110 provides the user interface withinformation which identifies at least one of the plurality of fielddevices for selection. Preferably, information for all the field devicesare provided. Then in Step 440, the commissioning tool 110 provides theuser interface with information which identifies at least one of aplurality of group types in the repository for selection. Preferably,information for all the group types are provided. In Step 450, thecommissioning tool 110 generates, using the selected template andselected group type, tasks associated with the check functions.

FIG. 7B is an example of workflow for performing step 420. In Step 421the commissioning tool 110 verifies if a connection check is applicableby using criteria for sequence 1 in Table 1. Step 422 verifies if alinearization check is applicable by using criteria for sequence 2 inTable 1. In Steps 423 and 424 the commissioning tool 110 verifies if aFF-H1 range check and HART range check are applicable by using criteriafor sequence 3 respectively in Table 1. In Steps 425 and 426, thecommissioning tool 110 verifies if an input loop check and output loopcheck are applicable by using criteria for sequences 4 and 5respectively in Table 1. In Step 427, the commissioning tool 110verifies if a manual check in Sequence 6 is applicable.

The above embodiments of the invention enable automatic generation oftasks to be performed. The association of the task and check functions,check functions and field devices are done automatically. This reducesman efforts required to identify and verify the check functions andtasks. With automation, human errors are reduced.

Further a standardized sequence of check function is generated. Byapplying a standardized sequence of check function and automating thegeneration of the sequence, human errors are reduced. Since priorconfiguration is done, the checks are done and results are recordedautomatically. Advantageously, the manpower is reduced and accordinglythere is achieved time and cost savings. With the reduction of the needfor manual field operations, there is reduced risk with less fieldoperators required.

In the field device commissioning system, the commissioning tool isconfigured to: provide the user interface with information which isassociated with at least one of a plurality of group types in therepository for selection; and generate, using a selected group type,tasks associated with the determined check functions for the selected atleast one field device.

In the field device commissioning system, the commissioning tool isconfigured to provide the user interface with information about thegenerated tasks associated with the determined check functions and theselected at least one field device.

In the field device commissioning system, the plurality of templates mayinclude, but is not limited to, a plurality of task templates andworkflow templates.

In the field device commissioning system, the task template includes atleast one predefined value for the task.

In the field device commissioning system, the workflow templateincludes: a predefined sequence of tasks for workflow; and for eachtask, at least one predefined value for the task.

In the field device commissioning system, the commissioning tool isconfigured to provide a user interface with an option to change the atleast one predefined value.

In the field device commissioning system, the commissioning tool isconfigured to communicate with a control system. The commissioning toolis further configured to determine, using an identifier in at least oneof a control system loop information file and a field device informationfile in the repository, a connection of the field device to the controlsystem.

In the field device commissioning system, the commissioning tool isconfigured to filter, using selected templates of the pluralitytemplates, the determined check functions to be supplied to the userinterface.

In another aspect of the invention, a field device commissioning methodperformed in a field device commissioning system may include, but is notlimited to, a commissioning tool. The commissioning tool beingconfigured to communicate with a plurality of field devices and arepository, the method may include, but is not limited to: providing auser interface with at least one of a plurality of templates in therepository for selection; determining, using at least one parameter inat least one of a control system loop information file and a fielddevice information file in the repository, check functions for the fielddevice; providing the user interface with information which identifiesat least one of the plurality of field devices for selection; andgenerating, using a selected template, tasks associated with thedetermined check functions for the selected at least one field device.

The method may include, but is not limited to: providing the userinterface with information which identifies at least one of a pluralityof group types in the repository for selection; and generating, using aselected group type, tasks associated with the determined checkfunctions for the selected at least one field device.

The method may include, but is not limited to: providing the userinterface with information about the generated tasks associated withdetermined check functions and the selected at least one field device.

In the method, the plurality of templates comprises a plurality of tasktemplates and workflow templates.

In the method, the task template includes at least one predefined valuefor the task.

The method may include, but is not limited to: providing an option tochange at least one of the predefined values.

The method may include, but is not limited to: determining, using anidentifier in the control system loop information file and the deviceinformation file, a connection of the field device to a control system.

In the method, determining check functions for the field device mayinclude, but is not limited to: verifying if a connection check isapplicable by using a first predefined criteria; verifying if alinearization check is applicable by using a second predefined criteria;verifying if a FF-H1 range check is applicable by using a thirdpredefined criteria; verifying if a HART range check is applicable byusing a fourth predefined criteria; verifying if an Input Loop Check isapplicable by using a fifth predefined criteria; and verifying if anoutput loop check is applicable by using a sixth predefined criteria;and wherein the first, second, third, fourth, fifth, and sixthpredefined criteria are different among others.

The method may include, but is not limited to: filtering, using selectedtemplates of the plurality templates, the determined check functions tobe to be supplied to the user interface.

In yet another aspect of the invention, a non-transitory computerreadable medium that stores a computer program to be executed by a fielddevice commissioning system to perform a field device commissioningmethod, the field device commissioning system may include, but is notlimited to, a commissioning tool. The commissioning tool beingconfigured to communicate with a plurality of field devices and arepository, the field device commissioning method may include, but isnot limited to: providing a user interface with at least one of aplurality of templates in the repository for selection; determining,using at least one parameter in at least one of a control system loopinformation file and a field device information file in the repository,check functions for the field device; providing the user interface withinformation which identifies at least one of the plurality of fielddevices for selection; and generating, using a selected template, tasksassociated with the determined check functions for the selected at leastone field device.

What is claimed is:
 1. A field device commissioning system, comprising acommissioning tool configured to communicate with a plurality of fielddevices and a repository: wherein the commissioning tool is configuredto: provide a user interface with at least one template of a pluralityof templates in the repository for selection; determine, using at leastone parameter in at least one of a control system loop information fileand a field device information file in the repository, check functionsfor at least one of the plurality of field devices; provide the userinterface with information which identifies at least one of theplurality of field devices for selection; and generate, using a selectedtemplate, tasks associated with the determined check functions for theselected at least one field device.
 2. The system as claimed in claim 1,wherein the commissioning tool is further configured to: provide theuser interface with information which is associated with at least one ofa plurality of group types in the repository for selection; andgenerate, using a selected group type, tasks associated with thedetermined check functions for the selected at least one field device.3. The system as claimed in claim 1, wherein the commissioning tool isfurther configured to provide the user interface with information aboutthe generated tasks associated with the determined check functions andthe selected at least one field device.
 4. The system in claim 1,wherein the plurality of templates comprises a plurality of tasktemplates and workflow templates.
 5. The system in claim 4, wherein thetask template includes at least one predefined value for the task. 6.The system in claim 4, wherein the workflow template includes: apredefined sequence of tasks for workflow; and for each task, at leastone predefined value for the task.
 7. The system in claim 5, wherein thecommissioning tool is further configured to provide a user interfacewith an option to change the at least one predefined value.
 8. Thesystem in claim 1, wherein the commissioning tool is configured tocommunicate with a control system, the commissioning tool is furtherconfigured to determine, using an identifier in at least one of acontrol system loop information file and a field device information filein the repository, a connection of the field device to the controlsystem.
 9. The system in claim 1, wherein the commissioning tool isfurther configured to filter, using selected templates of the pluralitytemplates, the determined check functions to be supplied to the userinterface.
 10. A field device commissioning method performed in a fielddevice commissioning system comprising a commissioning tool, thecommissioning tool being configured to communicate with a plurality offield devices and a repository, the method comprising: providing a userinterface with at least one of a plurality of templates in therepository for selection; determining, using at least one parameter inat least one of a control system loop information file and a fielddevice information file in the repository, check functions for the fielddevice; providing the user interface with information which identifiesat least one of the plurality of field devices for selection; andgenerating, using a selected template, tasks associated with thedetermined check functions for the selected at least one field device.11. The method in claim 10, further comprising: providing the userinterface with information which identifies at least one of a pluralityof group types in the repository for selection; and generating, using aselected group type, tasks associated with the determined checkfunctions for the selected at least one field device.
 12. The method inclaim 10, further comprising providing the user interface withinformation about the generated tasks associated with determined checkfunctions and the selected at least one field device.
 13. The method inclaim 10, wherein the plurality of templates comprises a plurality oftask templates and workflow templates.
 14. The method in claim 10,wherein the task template includes at least one predefined value for thetask.
 15. The method claimed in claim 14, further comprising providingan option to change at least one of the predefined values.
 16. Themethod in claim 10, further comprising determining, using an identifierin the control system loop information file and the device informationfile, a connection of the field device to a control system.
 17. Themethod in claim 10, wherein determining check functions for the fielddevice further comprises: verifying if a connection check is applicableby using a first predefined criteria; verifying if a linearization checkis applicable by using a second predefined criteria; verifying if aFF-H1 range check is applicable by using a third predefined criteria;verifying if a HART range check is applicable by using a fourthpredefined criteria; verifying if an Input Loop Check is applicable byusing a fifth predefined criteria; and verifying if an output loop checkis applicable by using a sixth predefined criteria; and wherein thefirst, second, third, fourth, fifth, and sixth predefined criteria aredifferent among others.
 18. The method in claim 10, further comprisingfiltering, using selected templates of the plurality templates, thedetermined check functions to be to be supplied to the user interface.19. A non-transitory computer readable medium that stores a computerprogram to be executed by a field device commissioning system to performa field device commissioning method, the field device commissioningsystem comprising a commissioning tool, the commissioning tool beingconfigured to communicate with a plurality of field devices and arepository, the field device commissioning method comprising: providinga user interface with at least one of a plurality of templates in therepository for selection; determining, using at least one parameter inat least one of a control system loop information file and a fielddevice information file in the repository, check functions for the fielddevice; providing the user interface with information which identifiesat least one of the plurality of field devices for selection; andgenerating, using a selected template, tasks associated with thedetermined check functions for the selected at least one field device.